Skip to main content

This is a new service – your feedback will help us to improve it.

Your data has issues

There is a problem

  • document-url column must have valid URIs
Reference Name Developer agreement type Planning application Document URL Notes Organisation Entry date Start date End date
S106-00542 section-106 PT14/3867/O

Invalid URI

2018-02-27 2018-02-27
S106-00543 section-106 PT14/3867/O

Invalid URI

2018-02-27 2018-02-27
S106-00544 section-106 PT14/3867/O

Invalid URI

2018-02-27 2018-02-27
S106-00545 section-106 PT14/3867/O

Invalid URI

2018-02-27 2018-02-27
S106-00546 section-106 PT14/3867/O

Invalid URI

2018-02-27 2018-02-27
S106-00547 section-106 PT14/3867/O

Invalid URI

2018-02-27 2018-02-27
S106-00548 section-106 PT14/3867/O

Invalid URI

2018-02-27 2018-02-27
S106-00549 section-106 PT14/3867/O

Invalid URI

2018-02-27 2018-02-27
S106-00550 section-106 PT14/3867/O

Invalid URI

2018-02-27 2018-02-27
S106-00551 section-106 PT14/3867/O

Invalid URI

2018-02-27 2018-02-27
S106-00471 section-106 PT14/3867/O

Invalid URI

2021-06-01 2021-06-01
S106-00294 section-106 PT17/4246/F

Invalid URI

2018-02-12 2018-02-12
S106-00316 section-106 PT16/3565/O

Invalid URI

2018-04-17 2018-04-17
S106-00317 section-106 PT16/3565/O

Invalid URI

2018-04-17 2018-04-17
S106-00318 section-106 PT16/3565/O

Invalid URI

2018-04-17 2018-04-17
S106-00319 section-106 PT16/3565/O

Invalid URI

2018-04-17 2018-04-17
S106-00320 section-106 PT16/3565/O

Invalid URI

2018-04-17 2018-04-17
S106-00321 section-106 PT16/3565/O

Invalid URI

2018-04-17 2018-04-17
S106-00625 section-106 PT16/3565/O

Invalid URI

2023-03-01 2023-03-01
S106-00666 section-106 PT16/3565/O

Invalid URI

2022-01-31 2022-01-31
S106-00284 section-106 PK17/3702/F

Invalid URI

2018-04-25 2018-04-25
S106-00286 section-106 PK17/3702/F

Invalid URI

2018-04-25 2018-04-25
S106-00288 section-106 PK17/3702/F

Invalid URI

2018-04-25 2018-04-25
S106-00291 section-106 PK17/4616/F

Invalid URI

2018-01-08 2018-01-08
S106-00345 section-106 PT17/2240/F

Invalid URI

2018-06-28 2018-06-28
S106-00424 section-106 PT17/2240/F

Invalid URI

2019-11-11 2019-11-11
S106-00425 section-106 PK17/5109/F

Invalid URI

2019-11-11 2019-11-11
S106-00307 section-106 PK17/5109/F

Invalid URI

2018-07-19 2018-07-19
S106-00311 section-106 PK17/5109/F

Invalid URI

2018-07-19 2018-07-19
S106-00389 section-106 PK17/5109/F

Invalid URI

2019-04-12 2019-04-12
S106-00304 section-106 PT17/0215/O

Invalid URI

2018-07-19 2018-07-19
S106-00346 section-106 PT16/6924/O

Invalid URI

2018-07-12 2018-07-12
S106-00352 section-106 PT16/6924/O

Invalid URI

2018-07-12 2018-07-12
S106-00354 section-106 PT16/6924/O

Invalid URI

2018-07-12 2018-07-12
S106-00421 section-106 PT16/6924/O

Invalid URI

2019-10-14 2019-10-14
S106-00335 section-106 PT16/4774/O

Invalid URI

2018-07-23 2018-07-23
S106-00336 section-106 PT16/4774/O

Invalid URI

2018-07-23 2018-07-23
S106-00299 section-106 PK18/1532/O

Invalid URI

2018-06-28 2018-06-28
S106-00418 section-106 PT17/2331/O

Invalid URI

2019-07-12 2019-07-12
S106-00313 section-106 PT17/2331/O

Invalid URI

2018-09-20 2018-09-20
S106-00337 section-106 PT18/0930/R3O

Invalid URI

2018-10-18 2018-10-18
S106-00338 section-106 PT18/0930/R3O

Invalid URI

2018-10-18 2018-10-18
S106-00340 section-106 PT18/0930/R3O

Invalid URI

2018-10-18 2018-10-18
S106-00330 section-106 PK17/4552/O

Invalid URI

2018-11-09 2018-11-09
S106-00468 section-106 PK17/4552/O

Invalid URI

2021-07-12 2021-07-12
S106-00371 section-106 PT16/6182/F

Invalid URI

2019-02-13 2019-02-13
S106-00374 section-106 PT17/3698/O

Invalid URI

2019-01-03 2019-01-03
S106-00387 section-106 MODT13/3223

Invalid URI

2018-03-15 2018-03-15
S106-00391 section-106 PT17/2006/O

Invalid URI

2019-03-01 2019-03-01
S106-00392 section-106 PT17/2006/O

Invalid URI

2019-03-01 2019-03-01

Showing rows 101 to 150 of 489

How to fix this issue

Your dataset is missing the document-url column.

The Developer agreement guidance explains how to fix the issue:

document-url

How to improve South Gloucestershire Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL